FISMA Compliance Handbook by Laura P. Taylor

Author:Laura P. Taylor
Language: eng
Format: epub, mobi
ISBN: 9780124059153
Publisher: Elsevier Inc.
Published: 2013-08-22T04:00:00+00:00

A Functional Baseline describes the architecture and functions of the system according to orignal specifications. The Functional Baselines contains all of the documentation that describes the systems features, performance, design, and architecture characteristics. Each document should be assigned a document ID number and include a publication date and the author name(s).

A Software Baseline contains and describes all of a system’s software. A Software Baseline includes the source code for each software configuration item and a software baseline document that provides a listing of the software and any other pertinent information such as developer, version, or software libraries. A Software Baseline locks in a version, build number, or release number at a particular moment in time.

A Product Baseline is the combination of the Functional Baseline and the Software Baseline. A product is not a product without documentation that explains how it works. A product could be an application that has been developed in-house or a commercial off-the-shelf application. Whether the product has been developed in-house or not, it should include installation and configuration information pertinent to the actual implementation. For a product developed in-house, the configuration management system should include the design and requirements documents. It’s not necessary to include design documents for commercial off-the-shelf products since companies will likely not give that out.

If any license keys are used in the baselines, you will want to state how license keys are archived and preserved. You should also include the agency security policies about using unlicensed software. What method is used to ensure that software license keys are not installed on systems that have not paid for the keys?

CM Analysts and Coordinators should establish new baselines at the end of the designand build phases in the system development life cycle and again at the end of the test phase. All baselines should be entered into the configuration management system. New baselines should be continuously sent to the Director of Configuration Management, or the designated individual that updates the configuration management system.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.